\chapter{Project Controlling | Tobias Langjahr}\label{chap:projectControlling}
Project controlling is a very important task within project management. The project controlling task is concerned with the monitoring of the project progress compared with the scheduled project plan presented in chapter \ref{chap:projectPlanning}. Project controlling is needed to detect any discrepancy between the project schedule and the project progress. In case of a discrepancy, the project manager or the whole team can react on the event which causes the discrepancy and find a solution to bring the project progress back in time. 

\noindent
This chapter will describe the project controlling task of the GreenGadget Inc. web shop project.


\section{Variance Comparison of Project Plan}
In this section the overall project progress is compared to the initially planned project plan in section \ref{sec:schedule}. Table \ref{tbl:variance} shows the defined milestones and when they have been reached. The highlighted milestone (Implementation Completed) is a milestones which had not been reached in time because of encountered problems during a work tasks. All other milestones where reached in time although one work task was delayed during the Requirements Engineering/Evaluation Phase. The encountered problems will be assessed within the following sections. 

\vspace{.5cm}
\begin{longtable}{p{65mm}|p{35mm}|p{35mm}}
 	\hline
 	\textbf{Milestone} & \textbf{Time Estimated} & \textbf{Time reached}\\
 	\hline
 	\hline
 	Project Planned & April, 9th 17:00 & April, 9th 17:00\\
 	\hline
 	Selection of a Shop System & April, 16th 09:00 & April, 16th 09:00\\
 	\hline
 	\rowcolor{grau}
 	Implementation Completed & April, 16th 13:00 & April, 16th 14:00\\
 	\hline
 	Submission of Report & June, 1st & June, 1st\\
 	\hline
	\caption{Variance Comparison of Project Plan}
	\label{tbl:variance}
\end{longtable}


\subsection{Assessment of Delays}
As already stated, one milestone had not been reached in time through problems of work tasks. The delayed work tasks will be critically assessed in the following.

\subsubsection{Selection of a Shop System}
\begin{description}
\item[Work Task: ]{Requirements Engineering}
\item[Delay: ]{1h}
\item[Reason:]{Through the variety of a web shop's use cases it was very difficult to define correct requirements for the project to meet the customer's needs.}
\item[Reaction:]{At this point the whole team was included within the requirements engineering process. Therefore it was not possible to rearrange resources. Facing that only a few requirements where missing, the decision was to finish the work task with a minimal delay.}
\item[Impact]{The impact on the project and the following milestone was seen as uncritical with the knowledge that only few requirements where missing. However, through the convenient presentations of the web shop providers (demo web shops) the evaluation of the shop systems was done faster than estimated and the milestone had been reached in time.}
\end{description}

\subsubsection{Implementation Completed}
\begin{description}
\item[Work Task: ]{Filling Content}
\item[Delay: ]{1h}
\item[Reason:]{As the chosen web shop system has a lot of additional settings for each product and general sites, this work task was slightly delayed.}
\item[Reaction:]{For this work item two team members where assigned. Therefore a third team member was assigned to this task.}
\item[Impact]{The impact on the project and the following milestone was seen as critical because of the scheduled final customer presentation. Luckily the milestone was planned to be achieved with some buffer time to the presentation. Therefore the web shop was fully functional for the presentation.}
\end{description}

\newpage
\section{Variance Comparison of Project Costs}
Based on the mentioned delays above, the actual project costs where higher than initially estimated. The following section will assess this cost differences.

\noindent
Table \ref{tbl:coststbl} shows the additional costs for the delayed work tasks which mount up to \euro{222,00}. It can be seen that the delayed task \textit{Requirements Engineering} did not add any costs because the work task \textit{Evaluation of Web Shop Systems} took less time.

\vspace{.5cm}
\begin{longtable}{p{50mm}|p{25mm}|p{25mm}|p{25mm}}
 	\hline
 	\textbf{Phase} & \textbf{$\Delta$ Resource} & \textbf{$\Delta$ Time} & \textbf{Costs}\\
 	\hline
 	Requirements Engineering & 0 & +1h & +\euro{00,00}\\
 	\hline
 	Selection of a Shop System & +3 & +1h & +\euro{222,00}\\
 	\hline
 	\hline
 	\textbf{Total}&&&\textbf{+\euro{222,00}}\\
 	\hline
	\caption{Variance Comparison of Project Costs}
	\label{tbl:coststbl}
\end{longtable}

 